=====================================================================
                           Link Check
                             v5.7
               Windows 3.x, Windows 95, Windows NT
                             Oct 1997
            Copyright (C) Karri Software Ltd 1994-1997
=====================================================================

 /*
 ** Installation Notes
 */

 It is recommended that all of the files contained in this package
 are unzipped to a single directory such as C:\LINKCHK. This will
 avoid any future versioning problems between different releases
 of the program(s).

 The Windows 95 version does not run under Windows NT due to Kernel
 differences between the two operating systems. Please use the NT
 version instead.


 /*
 ** What's New
 */

 There have been many changes made to the programs, the main highlights
 being:

 - Now fully functional
 - All version information now shown
 - Clipboard copy added for all info in tab-delimited form for easy export
 - "Ignore Modules in Memory" Option added
 - "Show Self-Registering Executables" Option added for identification of
   those files (32-bit only)
 - New interface
 - .OCXs are now shown correctly in the Windows NT version
 - New reports
 - New "Memory Details" display
 - Old executable (MZ) header display added
 - New executable (NE) header display added
 - Portable executable (PE) header display added (32-bit only)
 - Improved toolbar
 - Function Check displays can now be sorted
 - Ordinals in Function Check can now be displayed in decimal/hexadecimal
 - CTL3D32.DLL fix for Windows NT version
 - Can now self-register and unregister DLLs from the Registry (32-bit only)
 - Link Check can now create a response file for zipping purposes
 - Evaluation period extended to 30 days
 - Help files merged into just the one (WLCHECK.HLP)
 - Other minor bugs fixed

 Also please visit our new Web page:

           http://ourworld.compuserve.com/homepages/KarriSL

 /*
 ** Introduction
 */

 Link Check is a suite of three (3) diagnostic programs which allows
 the user to examine different areas of the system. These are useful
 not only on solving system problems but also for learning about the
 system.

 All three programs show version and file information on any of the
 modules (files) for identification purposes as well as interacting
 with each other.

 Armed with these three, you should be able to solve most of your
 software problems:


 /*
 ** 1) Link Check
 */

 Link Check enables the user to view the links between an executable
 file and the modules it requires to run on the system. This tool is
 useful for analyzing those "Cannot find (filename) or one of its
 components" system error messages.

 You may also use Link Check to view which versions of modules (DLLs,
 VBXs, OCXs) the program will actually use in the system as there are
 duplicate DLLs frequently lying about the network or the machine.

 Link Check mimics the system when a program is finally executed by the
 operating system (Windows). This will help in determining beforehand
 whether a program will run or not, or which particular copy of a .DLL
 it is going to use if there are multiple copies lying around the system.

 Any file(s) required by the program that are missing from the system will
 be highlighted with a red exclamation mark. It could be that the file(s)
 are actually present on the system but will not get picked up by the system
 during run time. This could be because the system environment variable PATH
 has been changed.

 Link Check is also useful for analyzing software installation problems
 as well as indicating which support modules should be backed-up with a
 particular program.


 /*
 ** 2) Memory Check
 */

 Memory Check allows the user to view, load and unload modules currently
 in memory. You may also view the current status of memory, including the
 amount of free memory left.

 Important version information about each module can be displayed and you
 may create and print a summary report of the state of the system.

 Memory Check really comes into play when some program has ended abnormally
 and has left modules lying around in memory. The system might behave
 irratically but more to the point, those modules take up valuable memory.
 In these situations you can use Memory Check to unload those modules and
 save a reboot of Windows.

 Warning: Sometimes a clean unload is not possible and you may find yourself
 unceremoniously dumped back on to the C: prompt, so please do use care when
 unloading.

 You may also verify exactly which version of a module is currently loaded
 in memory. Sometimes some programs will not run because a wrong version of
 a particular module (.DLL) has already been loaded into memory by some
 other application. Windows does not load a new copy of a file with the same
 file name but will simply increase the "usage count" of the module already
 in memory. These "usage counts" are displayed by Memory Check as a number
 in parenthesis () after the file name.

 WINSOCK.DLL is a very good example of a module which shares very many
 different versions. Most communications programs require their own particular
 version of WINSOCK.DLL to be loaded, but if another application has put
 their version in first, it is highly likely that the second one will fail
 or behave in manner not designed by the programmers. Use Memory Check to
 solve these type of problems.


 /*
 ** 3) Function Check
 */

 Function Check allows the user to view actual function calls inside
 modules. This program is useful for analyzing those "Call to Undefined
 Dynalink" system error messages.

 When a program calls a module (.DLL) to execute a function (piece of
 code) inside the .DLL and that particular function does not exist in
 the .DLL, a "Call to Undefined Dynalink" error is raised by the system.
 These can occur when a newer version of a .DLL is accidentally replaced
 by an older version of the same .DLL. A program is compiled to use the new
 functionality of the .DLL but can come unstuck when that .DLL is replaced
 by an older version which does not contain the new functionality.

 Some installation programs are prone to do this "accidental" replacement.

 Function Check cross-checks all function calls in an executable with
 the ones in all of the .DLLs (modules) that it uses, to verify that
 all of the functions all present.

 Should your program throw up one of those "Call to Undefined Dynalink"
 messages, Function Check will show you which module is at fault.


 /*
 ** How to Register/Order
 */

 Please see the "About" dialog box and click on the "Ordering Information"
 pushbutton.

 Alternatively, please see the online Help file for the same section
 obtainable from the "Contents" page.

 If all else fails, please visit our Web page:

           http://ourworld.compuserve.com/homepages/KarriSL

 /*
 ** Registered Version
 */

 You have the registered version. Some features are disabled and you
 have a 30-day evaluation period to test the program. Should you
 decide to register we will email you a license file which will give
 you full access to all of the features as well as removing the time
 limit. This license file will also work across different releases;
 you only need to obtain it once. Should you lose it or should it
 become corrupt, please email us and we will send you a new copy.


 /*
 ** Price Details
 */

 Link Check for Windows 3.x   - $29
 Link Check for Windows 95    - $35
 Link Check for Windows NT    - $35
 Link Check Suite (all three) - $50

 Note that all future upgrades are free.


 /*
 ** Technical Support
 */

 The Windows Utility forum on CompuServe (GO WINUTIL) is now the
 official home of Link Check. You may pass any questions on to
 their online staff.

 You can always get in touch with us too, please email any questions
 to:

                   KarriSL@compuserve.com

